| Package | ForgePatientChart.0830 |
| Type | StructureDefinition |
| Id | Id |
| FHIR Version | R4 |
| Source | https://simplifier.net/resolve?scope=ForgePatientChart.0830@0.1.0&canonical=https://telus.com/fhirpatientChart//StructureDefinition/profile-provenance |
| Url | https://telus.com/fhirpatientChart//StructureDefinition/profile-provenance |
| Status | draft |
| Name | Provenance |
| Experimental | False |
| Authority | hl7 |
| Type | Provenance |
| Kind | resource |
No resources found
No resources found
FHIR{
"resourceType" : "StructureDefinition",
"url" : "https://telus.com/fhirpatientChart//StructureDefinition/profile-provenance",
"name" : "Provenance",
"status" : "draft",
"fhirVersion" : "4.0.1",
"mapping" : [
{
"identity" : "workflow",
"uri" : "http://hl7.org/fhir/workflow",
"name" : "Workflow Pattern"
},
{
"identity" : "rim",
"uri" : "http://hl7.org/v3",
"name" : "RIM Mapping"
},
{
"identity" : "w3c.prov",
"uri" : "http://www.w3.org/ns/prov",
"name" : "W3C PROV"
},
{
"identity" : "w5",
"uri" : "http://hl7.org/fhir/fivews",
"name" : "FiveWs Pattern Mapping"
},
{
"identity" : "fhirauditevent",
"uri" : "http://hl7.org/fhir/auditevent",
"name" : "FHIR AuditEvent Mapping"
}
],
"kind" : "resource",
"abstract" : false,
"type" : "Provenance",
"baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Provenance",
"derivation" : "constraint",
"differential" : {
"element" : [
{
"id" : "Provenance",
"path" : "Provenance",
"comment" : "*** add provenance comment extension\r\n\r\nConformance Rule: Provenance IS ALWAYS present when sharing a medication “with history”. Provenance is never present when sharing a medication without history (eg the current state)\r\n\r\nSome parties may be duplicated between the target resource and its provenance. For instance, the prescriber is usually (but not always) the author of the prescription resource. This resource is defined with close consideration for W3C Provenance.",
"mustSupport" : true
},
{
"id" : "Provenance.meta",
"path" : "Provenance.meta",
"mustSupport" : true
},
{
"id" : "Provenance.meta.lastUpdated",
"path" : "Provenance.meta.lastUpdated",
"mustSupport" : true
},
{
"id" : "Provenance.meta.source",
"path" : "Provenance.meta.source",
"mustSupport" : true
},
{
"id" : "Provenance.meta.profile",
"path" : "Provenance.meta.profile",
"mustSupport" : true
},
{
"id" : "Provenance.text",
"path" : "Provenance.text",
"comment" : "Usage Note: The text must include all data that is clinically relevant; this may be displayed to the user along with text from other resources such as the Medication Plan. This must include tall items that are \"must support\"he target.display, occurred, recorded, reason, activity\r\n\r\nContained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later.",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Provenance.target",
"path" : "Provenance.target",
"mustSupport" : true
},
{
"id" : "Provenance.target.reference",
"path" : "Provenance.target.reference",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Provenance.target.display",
"path" : "Provenance.target.display",
"comment" : "Usage: This should contain the text \"Plan for x\", where x is the name of the medication name (eg .Medication.code.text)\r\n\r\nThis is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Provenance.occurred[x]",
"path" : "Provenance.occurred[x]",
"comment" : "Usage Note: This is the actual date and time that the activity occurred. Example: The patient stopped taking the medicaiton on January 1st; this was recorded at the patient visit on January 15th. The occurred date is January 1st. \r\n \r\nExample: The occurred date may be different from the recorded date if the EMR is unavailable when the practitioner actions a change.\r\n\r\nThe period can be a little arbitrary; where possible, the time should correspond to human assessment of the activity time.",
"min" : 1,
"type" : [
{
"code" : "dateTime"
}
],
"mustSupport" : true
},
{
"id" : "Provenance.recorded",
"path" : "Provenance.recorded",
"mustSupport" : true
},
{
"id" : "Provenance.reason",
"path" : "Provenance.reason",
"comment" : "Usage Note: The reason is optional as it may not be recorded discretely as a reason in the exporting system. This should only be used by sending systems who can discretely capture a reason for the acitvity. \r\n\r\nExample: Activity might be DISCONTINUED (state change) and the reason may be explicity captured, eg \"Patient Stopped Medication\". \r\n\r\n Example 2: If the EMR captures a medication change comment in the same dialogue as the activity (eg Medication Change), the reason may be captured here. \"on hold due to surgery\", \"current dosages too low\" \r\n\r\nUsage Note: The EMRs support coding in some circumstances, eg ON MD mandates codified values for discontinue/termination. (Gavin to validate). \r\n\r\nUsage Note: In the context of an \"export\" (activity=export), the reason may include values such as \"Complete Patient Chart with full history\", or \"Partial Patient Chart\", IPS Export, eReferral Export, Other\r\n\r\nConformance Rule: The reason must be replicated in the MedicationPlan.notes. Rationale: Provenance is not always shared.\r\n\r\nPSS: Comments field - comments captured at time of dosage change reason\r\n\r\nNot all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.",
"mustSupport" : true
},
{
"id" : "Provenance.reason.coding",
"path" : "Provenance.reason.coding",
"comment" : "Usage Note: EMRs are not capturing this information discretely today.\r\n\r\nCodes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.",
"mustSupport" : true
},
{
"id" : "Provenance.reason.coding.system",
"path" : "Provenance.reason.coding.system",
"mustSupport" : true
},
{
"id" : "Provenance.reason.coding.code",
"path" : "Provenance.reason.coding.code",
"mustSupport" : true
},
{
"id" : "Provenance.reason.text",
"path" : "Provenance.reason.text",
"comment" : "Usage Note; \r\n\r\nVery often the text is the same as a displayName of one of the codings.",
"mustSupport" : true
},
{
"id" : "Provenance.activity",
"path" : "Provenance.activity",
"comment" : "Conformance Rule: The EMR may not have a record of when the activity occurred and in this case may use the recorded date in its place. This can support a partial date if that is all that is known. \r\n\r\nConformance Rule: If the sending system recognizes that a medication will auto-complete on a certain date, a provenance should be created in order to record this, using a code of \"medication completion\". This is a system level activity versus a clinical discontinuation, which uses an activity code of \"discontinue\".\r\n\r\nConformance Rule: Period may be useful when there is a fuzzy date and the exact date is not known\r\n\r\nExample: Medication Change (eg dosage change), or \"auto-complete\" for a short-term drug plan.\r\n\r\nConformance Rule: Activity must be codified ***VALUE SET TO BE UPDATED TO A MEDICAITON-SPECIFIC VALUE SET\r\n\r\nConformance Rule: Set value = \"export patient chart\" at the bundle level, as an overall activity for the patient chart\r\n\r\nNot all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Provenance.activity.coding",
"path" : "Provenance.activity.coding",
"min" : 1,
"max" : "1",
"mustSupport" : true
},
{
"id" : "Provenance.activity.coding.system",
"path" : "Provenance.activity.coding.system",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Provenance.activity.coding.code",
"path" : "Provenance.activity.coding.code",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Provenance.activity.text",
"path" : "Provenance.activity.text",
"comment" : "Usage Rule: Notes recorded that are assocaited with the activity. Example: If there is a Medication Update, the physicians notes associated with the transaction\r\n\r\nPSS: If a medication is changed, a transaction is added to the journal, CHANGE TO: (dose, quantity, refills, instructions. If comments or compliance or success are part of the change, they can be included. \r\nPSS: If a comment or compliance or success is added without a medication change, it is called a COMMENTS ABOUT.\r\n\r\n\r\nVery often the text is the same as a displayName of one of the codings.",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Provenance.agent",
"path" : "Provenance.agent",
"comment" : "Conformance Rule: One or more iistances of WHO may be specified; this will be a reference to the user who carried out the action. \r\n\r\nConformance Rule: If the PractitionerRole resource can be populated, this must be specified as the role is clinically important. The PractitionerRole should always reference the Practitioner resource. Organization can be referenced from PractitionerRole and becomes important when the organization is external. Lastly, if the practitioner role cannot be determined, the Practitioner resource is permitted.\r\n\r\nConformance Rule: In the case of an auto-complete, the agent specified must be the last user to prescribe or renew or start a medication.\r\n\r\nUsage Note: On an import, the agent data may be limited and EMRs should specify what they can.\r\nUsage Note: For external agents, a who.display value of \"external\" may be used.\r\nUsage Note: For the bundle level \"export\" provenance, who should always be the practitioner role, with references to practitioner and organization.\r\n\r\nMapping PSS: Uses two sets of initials; the first is the \"doctor initials\", such as physician/nurse practitioner responsible for the \"patient piece\", aka transaction/note/medication update. If the doctor is the only person who touched a record, only the first set of initials will be included.\r\nThe second set of initials is the \"user initials\". This is the last person who touched the patient piece other than doctor. If there are two sets of initials, both will be sent as two agents. The initials will be converted into a full name and populated in the practitioner resource; the associated role will be specified in PractitionerRole.\r\nSeveral agents may be associated (i.e. has some responsibility for an activity) with an activity and vice-versa.",
"mustSupport" : true
},
{
"id" : "Provenance.agent.who",
"path" : "Provenance.agent.who",
"comment" : "Conformance Rule: In the case of an auto-discontinue activity, the creator of the latest prescription or renewal.\r\nConformance Rule: The practitionerRole, including Practitoner and Organization references must be specified where known. \r\n\r\nwhoIdentity should be used when the agent is not a Resource type.",
"type" : [
{
"code" : "Reference",
"aggregation" : [
"bundled"
]
}
],
"mustSupport" : true
},
{
"id" : "Provenance.agent.who.reference",
"path" : "Provenance.agent.who.reference",
"mustSupport" : true
},
{
"id" : "Provenance.agent.who.display",
"path" : "Provenance.agent.who.display",
"comment" : "Conformance Rule: If the EMR has imported a record from an external source, this can be populated with a value of \"external\"\r\n\r\nThis is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.",
"mustSupport" : true
},
{
"id" : "Provenance.agent.onBehalfOf",
"path" : "Provenance.agent.onBehalfOf",
"comment" : "Usage Note: There are no known use cases at this time for Organization (future use)\r\n\r\nonBehalfOfIdentity should be used when the agent is not a Resource type.",
"type" : [
{
"code" : "Reference",
"targetProfile" : [
"http://hl7.org/fhir/StructureDefinition/Practitioner",
"http://hl7.org/fhir/StructureDefinition/PractitionerRole",
"http://telus.com/fhir/StructureDefinition/profile-organization-patientchart"
],
"aggregation" : [
"bundled"
]
}
]
},
{
"id" : "Provenance.entity",
"path" : "Provenance.entity",
"comment" : "Usage Rule: In the context of sharing medication in the patient chart, this may be used to reference a medication order that is associated with the Plan. Example: The presence of a Medication Order (Prescription) or a Medicaiton Statement (stored as a Medication record in the EMR) will trigger the creation of a plan",
"mustSupport" : true
},
{
"id" : "Provenance.entity.role",
"path" : "Provenance.entity.role",
"mustSupport" : true
},
{
"id" : "Provenance.entity.what",
"path" : "Provenance.entity.what",
"type" : [
{
"code" : "Reference",
"targetProfile" : [
"http://telus.com/fhir/StructureDefinition/profile-medication-request-order-patient-chart",
"http://telus.com/fhir/StructureDefinition/profile-medicationStatement-patientchart"
]
}
],
"mustSupport" : true
},
{
"id" : "Provenance.entity.what.reference",
"path" : "Provenance.entity.what.reference",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Provenance.entity.what.display",
"path" : "Provenance.entity.what.display",
"comment" : "Usage: Note: If the entity.what is a reference to http://telus.com/fhir/StructureDefinition/profile-medication-request-order-patient-chart this should contain the text \"Prescription for x\", where \"x\" is the name of the medication name (eg .Medication.code.text) from the Medication Order. \r\n\r\nUsage Note: If the entity.what is a reference to http://telus.com/fhir/StructureDefinition/profile-medicationStatement-patientchart this should contain the text \"Patient Statement for x\", where \"x\" is the name of the medication name (eg .Medication.code.text) from the Medication Statement.\r\n\r\nThis is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.",
"min" : 1,
"mustSupport" : true
},
{
"id" : "Provenance.entity.agent",
"path" : "Provenance.entity.agent",
"contentReference" : "http://hl7.org/fhir/StructureDefinition/Provenance#Provenance.agent"
}
]
},
"text" : {
}
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.